Repository navigation
Coverage report: orange for untested lines, blue for full coverage - #40
Merged
Merged
Conversation
The two states of the coverage after Tests can now be told apart at a glance. Lines no example ran get the colours of their marks in the IDE's editor (--glp-warning-bg, --glp-warning bar). Full coverage gets a light blue info box (new tokens --glp-info-bg #E3EEFA, --glp-info #1D5B9A): distinct from the grey console, and never green like «bestanden», since covered code can still be wrong. Texts and behaviour are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P23 follow-up, the instructor's decision of 2026-10-29: the coverage report's two states can be told apart at a glance. Texts, behaviour,
check-runtime-coverage.pyand the protocol are unchanged; only styling.Changes
--glp-warning-bgwith a--glp-warningbar on the left. These are the colours of the line marks in the IDE's editor, so box and marks belong together.--glp-info-bg#E3EEFAand--glp-info#1D5B9A(bar). Not green, unlike the «n von n Beispielen bestanden» line above it.style.css.Contrast (WCAG 2.x, light theme)
--glp-text#1A1A1A on--glp-warning-bg#FFF4E5--glp-info-bg#E3EEFAThe pale fills differ from the grey console mainly in hue (lightness ratio 1.01–1.07:1). The bars and the heading text carry the distinction, so colour is never the only signal.
Dark mode
glpython has no dark theme. All
--glp-*tokens exist only in light, Monaco uses the lightvsbase, and the macro keeps the block light in LiaScript's dark mode on purpose. So the info tokens are light-only like all others, and there are no dark-mode screenshots. A dark theme would be its own piece of work (all tokens plus the Monaco theme).Checked
test:console(Chrome, Pyodide).bewertung(orange box, and in the IDE the mark on line 11) andist_genuegend(blue box).After the merge: tag
v0.1.18, then the IDE bump.🤖 Generated with Claude Code